-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dashboard] EUI Visual Refresh Integration #204442
[Dashboard] EUI Visual Refresh Integration #204442
Conversation
a63e9e5
to
fd9b122
Compare
bb1f68c
to
bddbc7d
Compare
bddbc7d
to
6d69138
Compare
.../presentation_panel/public/panel_component/panel_header/presentation_panel_hover_actions.tsx
Outdated
Show resolved
Hide resolved
@@ -142,11 +147,11 @@ export const PresentationPanelHoverActions = ({ | |||
const hoverActionsWidth = | |||
(rightHoverActionsRef.current?.offsetWidth ?? 0) + | |||
(dragHandleRef.current?.offsetWidth ?? 0) + | |||
parseInt(euiThemeVars.euiSize, 10) * 2; | |||
parseInt(euiTheme.size.m, 10) * 2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably be euiTheme.size.base
as euiSize
was 16px
and euiTheme.size.m
is 12px
(same for the following occurrences)
.../presentation_panel/public/panel_component/panel_header/presentation_panel_hover_actions.tsx
Outdated
Show resolved
Hide resolved
position: absolute; | ||
top: 0; | ||
display: flex; | ||
justify-content: space-between; | ||
padding: 0 ${euiThemeVars.euiSize}; | ||
padding: 0 ${euiTheme.size.medium}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking euiTheme.size.medium
does not exists. Based on the original value, this likely should be euiTheme.size.base
.
Pinging @elastic/kibana-presentation (Team:Presentation) |
|
||
const { euiTheme } = useEuiTheme(); | ||
|
||
const EDIT_MODE_OUTLINE = `${euiTheme.border.width.thin} dashed ${euiTheme.colors.borderBaseFormsControl}`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use useMemo
to avoid recreating these string on each render.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think useMemo
usage is best left to things which are expensive to compute. useMemo
itself can introduce overhead .
…://github.com/cqliu1/kibana into borealis/dashboard/replace-euiThemeVars-usage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Changes LGTM from EUI side
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]Async chunks
Page load bundle
History
|
## Summary Related to elastic#203132. Closes elastic#204590. This replaces all references to euiThemeVars in favor of the useEuiTheme hook in the dashboard plugin. This also updates ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Summary
Related to #203132.
Part of #204590.
This replaces all references to euiThemeVars in favor of the useEuiTheme hook in the dashboard plugin. This also updates the color of the presentational panel border in edit mode from
mediumShade
, which was deprecated, toBorderBaseFormsControl
as the darker border color.Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breaking
label should be applied in these situations.release_note:*
label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.